Proximity event determination with lane change information

ABSTRACT

A system for determining proximity events includes an input interface and a processor. The input interface is to receive a lane change information. The processor is to determine a proximity event based at least in part on the lane change information.

BACKGROUND OF THE INVENTION

Modern vehicles (e.g., airplanes, boats, trains, cars, trucks, etc.) caninclude a vehicle event recorder in order to better understand thetimeline of an anomalous event (e.g., an accident). A vehicle eventrecorder typically includes a set of sensors, e.g., video recorders,audio recorders, accelerometers, gyroscopes, vehicle state sensors, GPS(global positioning system), etc., that report data, which is used todetermine the occurrence of an anomalous event. Sensor data can then betransmitted to an external reviewing system. Anomalous event typesinclude accident anomalous events, maneuver anomalous events, locationanomalous events, proximity anomalous events, vehicle malfunctionanomalous events, driver behavior anomalous events, or any otheranomalous event types. However, when new sensors are developed, theyneed to be incorporated into the detection system for anomalous events.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the invention are disclosed in the followingdetailed description and the accompanying drawings.

FIG. 1 is a block diagram illustrating an embodiment of a systemincluding a vehicle event recorder.

FIG. 2 is a block diagram illustrating an embodiment of a vehicle eventrecorder.

FIG. 3 is a block diagram illustrating an embodiment of an eventdetector.

FIG. 4 is a block diagram illustrating an embodiment of a sensorinterface.

FIG. 5 is a block diagram illustrating an embodiment of a proximityevent system.

FIG. 6 is a diagram illustrating an embodiment of proximity data showinga proximity event.

FIG. 7 is a diagram illustrating an embodiment of proximity data showinga cut off event.

FIG. 8 is a diagram illustrating an embodiment of proximity data showinga lane change event performed by the host vehicle.

FIG. 9 is a flow diagram illustrating an embodiment of a process fordetermining proximity events.

FIG. 10 is a flow diagram illustrating an embodiment of a process fordetermining lane change information.

FIG. 11 is a flow diagram illustrating an embodiment of a process fordetermining a proximity event based at least in part on lane changeinformation.

FIG. 12 is a flow diagram illustrating an embodiment of a process fordetermining whether to provide a proximity event based at least in parton lane change information.

FIG. 13 is a flow diagram illustrating an embodiment of a process fordetermining a sustained proximity time threshold.

DETAILED DESCRIPTION

The invention can be implemented in numerous ways, including as aprocess; an apparatus; a system; a composition of matter; a computerprogram product embodied on a computer readable storage medium; and/or aprocessor, such as a processor configured to execute instructions storedon and/or provided by a memory coupled to the processor. In thisspecification, these implementations, or any other form that theinvention may take, may be referred to as techniques. In general, theorder of the steps of disclosed processes may be altered within thescope of the invention. Unless stated otherwise, a component such as aprocessor or a memory described as being configured to perform a taskmay be implemented as a general component that is temporarily configuredto perform the task at a given time or a specific component that ismanufactured to perform the task. As used herein, the term ‘processor’refers to one or more devices, circuits, and/or processing coresconfigured to process data, such as computer program instructions.

A detailed description of one or more embodiments of the invention isprovided below along with accompanying figures that illustrate theprinciples of the invention. The invention is described in connectionwith such embodiments, but the invention is not limited to anyembodiment. The scope of the invention is limited only by the claims andthe invention encompasses numerous alternatives, modifications andequivalents. Numerous specific details are set forth in the followingdescription in order to provide a thorough understanding of theinvention. These details are provided for the purpose of example and theinvention may be practiced according to the claims without some or allof these specific details. For the purpose of clarity, technicalmaterial that is known in the technical fields related to the inventionhas not been described in detail so that the invention is notunnecessarily obscured.

A system for determining proximity events comprises an input interfacefor receiving a lane change information and a processor for determininga proximity event based at least in part on the lane change information.In some embodiments, the system for determining proximity eventsadditionally comprises a memory coupled to the processor and configuredto provide the processor with instructions.

In some embodiments, a system for determining proximity events comprisesa vehicle event recorder coupled to a proximity sensor for determiningforward proximity measurements. The proximity sensor provides theforward proximity measurements to a proximity event system and a lanechange determiner. In some embodiments, the proximity event systemdetermines and provides proximity events based at least in part on theforward proximity measurements and on lane change determinations fromthe lane change determiner, where a determination of proximity eventsbased on proximity measurements and on lane change determinations is animprovement over events based only on proximity measurements. Proximityevents comprise anomalous events determined by a vehicle event recorderfor a vehicle that follows too closely the vehicle in front of it. Thelane change determiner provides lane leaving events (e.g., an event inwhich a vehicle with a vehicle event recorder leaves a lane or movesover a lane marker) and cut off events (e.g., an event in which avehicle changes lanes immediately in front of the vehicle with a vehicleevent recorder). In some embodiments, in the event a lane change eventoccurs near in time to a proximity event, the proximity event is notprovided as an event (e.g., not transferred to a server as an event, notstored at a server as an event, etc.). In some embodiments, in the eventa vehicle comes within the proximity time threshold of the vehiclepreceding it (e.g., gets too close to the car in front) then shiftslanes within a sustained proximity time threshold (e.g., changes lanesafter just a short time of being too close), the proximity event is notprovided as an event (e.g., not transferred to a server as an event, notstored at a server as an event, etc.). In some embodiments, in the eventthat a vehicle is cut off by a vehicle shifting into its lane butincreases the following distance to greater than the proximity timethreshold within an extended sustained proximity time threshold, theproximity event is not provided as an event (e.g., not transferred to aserver as an event, not stored at a server as an event, etc.).

FIG. 1 is a block diagram illustrating an embodiment of a systemincluding a vehicle event recorder. Vehicle event recorder 102 comprisesa vehicle event recorder mounted in a vehicle (e.g., a car or truck). Insome embodiments, vehicle event recorder 102 includes or is incommunication with a set of sensors—for example, video recorders, audiorecorders, accelerometers, gyroscopes, vehicle state sensors, proximitysensors, a global positioning system (e.g., GPS), outdoor temperaturesensors, moisture sensors, laser line tracker sensors, or any otherappropriate sensors. In various embodiments, vehicle state sensorscomprise a speedometer, an accelerator pedal sensor, a brake pedalsensor, an engine revolutions per minute (e.g., RPM) sensor, an enginetemperature sensor, a headlight sensor, an airbag deployment sensor,driver and passenger seat weight sensors, an anti-locking brake sensor,an engine exhaust sensor, a gear position sensor, a cabin equipmentoperation sensor, or any other appropriate vehicle state sensors. Insome embodiments, vehicle event recorder 102 comprises a system forprocessing sensor data and detecting events. In some embodiments,vehicle event recorder 102 comprises map data. In some embodiments,vehicle event recorder 102 comprises a system for detecting riskybehavior. In some embodiments, vehicle event recorder 102 comprises asystem for detecting vehicle proximity events. In various embodiments,vehicle event recorder 102 is mounted on vehicle 106 in one of thefollowing locations: the chassis, the front grill, the dashboard, therear-view mirror, or any other appropriate location. In someembodiments, vehicle event recorder 102 comprises multiple units mountedin different locations in vehicle 106. In some embodiments, vehicleevent recorder 102 comprises a communications system for communicatingwith network 100. In various embodiments, network 100 comprises awireless network, a wired network, a cellular network, a code divisionmultiple access (CDMA) network, a global System for Mobile Communication(GSM) network, a Long-Term Evolution (LTE) network, a Universal MobileTelecommunications System (UMTS) network, a Worldwide Interoperabilityfor Microwave Access (WiMAX) network, a Dedicated Short-RangeCommunications (DSRC) network, a local area network, a wide areanetwork, the Internet, or any other appropriate network. In someembodiments, network 100 comprises multiple networks, changing over timeand location. In some embodiments, different networks comprising network100 comprise different bandwidth cost (e.g., a wired network has a verylow cost, a wireless Ethernet connection has a moderate cost, a cellulardata network has a high cost). In some embodiments, network 100 has adifferent cost at different times (e.g., a higher cost during the dayand a lower cost at night). Vehicle event recorder 102 communicates withvehicle data server 104 via network 100. Vehicle event recorder 102 ismounted to vehicle 106. In various embodiments, vehicle 106 comprises acar, a truck, a commercial vehicle, or any other appropriate vehicle.Vehicle data server 104 comprises a vehicle data server for collectingevents and risky behavior detected by vehicle event recorder 102. Insome embodiments, vehicle data server 104 comprises a system forcollecting data from multiple vehicle event recorders. In someembodiments, vehicle data server 104 comprises a system for analyzingvehicle event recorder data. In some embodiments, vehicle data server104 comprises a system for displaying vehicle event recorder data. Insome embodiments, vehicle data server 104 is located at a home station(e.g., a shipping company office, a taxi dispatcher, a truck depot,etc.). In some embodiments, events recorded by vehicle event recorder102 are downloaded to vehicle data server 104 when vehicle 106 arrivesat the home station. In various embodiments, vehicle data server 104 islocated at a colocation center (e.g., a data center where equipment,space and bandwidth are available for rental), at a cloud serviceprovider, at a remote location, or any other appropriate location. Insome embodiments, events recorded by vehicle event recorder 102 aredownloaded to vehicle data server 104 wirelessly. In some embodiments, asubset of events recorded by vehicle event recorder 102 is downloaded tovehicle data server 104 wirelessly. In some embodiments, vehicle eventrecorder 102 comprises a system for managing a camera.

FIG. 2 is a block diagram illustrating an embodiment of a vehicle eventrecorder. In some embodiments, vehicle event recorder 200 of FIG. 2comprises vehicle event recorder 102 of FIG. 1. In the example shown,vehicle event recorder 200 comprises communications 202. In variousembodiments, communications 202 comprises local communications (e.g.,communications with a driver, passenger, vehicle technician, etc.),remote communications (e.g., communications over a network), wiredcommunications, wireless communications, communications over a GlobalSystem for Mobile (e.g., GSM) network, communications over a CodeDivision Multiple Access (e.g., CDMA) network, communications over acellular network, communications over a WiFi network, communicationsover an Ethernet network, communications over a Universal Serial Bus(e.g., USB), communications over Bluetooth, communications over theInternet, communications using LTE, communications using UMTS,communications using WiMax, communications using DSRC, or any otherappropriate communications. In some embodiments, communications 202 isimplemented as an interface. In some embodiments, communications 202 isimplemented using a processor. Sensor interface 204 comprises aninterface to one or more vehicle event recorder sensors. In variousembodiments, vehicle event recorder sensors comprise an external videocamera, an internal video camera, a microphone, an accelerometer, agyroscope, an outdoor temperature sensor, a moisture sensor, a laserline tracker sensor, vehicle state sensors, or any other appropriatesensors. In various embodiments, vehicle state sensors comprise aspeedometer, an accelerator pedal sensor, a brake pedal sensor, anengine RPM sensor, a distance to forward vehicle sensor, a proximitysensor, an engine temperature sensor, a headlight sensor, an airbagdeployment sensor, driver and passenger seat weight sensors, ananti-locking brake sensor, an engine exhaust sensor, a gear positionsensor, a cabin equipment operation sensor, or any other appropriatevehicle state sensors. In some embodiments, sensor interface 208comprises an on-board diagnostics (OBD) bus (e.g., society of automotiveengineers (SAE) J1939, J1708/J1587, OBD-II, CAN BUS, etc.). In someembodiments, sensor interface 204 is implemented using a processor. Insome embodiments, vehicle event recorder 200 communicates with vehiclestate sensors via OBD bus. Event detector 206 comprises an eventdetector for detecting anomalous events. In various embodiments,anomalous events comprise accident events, maneuver events, proximityevents, or any other appropriate anomalous events. In some embodiments,anomalous events are determined based at least in part on sensor data(e.g., sensor data received via sensor interface 204). In someembodiments, event detector 206 is implemented using a processor. Invarious embodiments, the elements of vehicle event recorder 200 areimplemented all on a single processor, each on their own processor, orcombined on multiple processors in any appropriate way. In someembodiments, vehicle event recorder 200 additionally comprises a memorycoupled to the one or more processors. In various embodiments, thememory comprises a magnetic memory, an optical memory, a solid-statememory, a flash memory, a non-volatile memory, a read-only memory, atape memory, a disc memory, or any other appropriate memory.

FIG. 3 is a block diagram illustrating an embodiment of an eventdetector. In some embodiments, event detector 300 comprises eventdetector 206 of FIG. 2. In the example shown, event detector 300comprises a set of event systems (e.g., accident event system 302,maneuver event system 304, and proximity event system 306). Eventsystems comprise systems for detecting events using sensor data. In someembodiments, accident event system 302 comprises a system for detectingaccident events using accelerometer data. In some embodiments, accidentevent system 302 is implemented using a processor. In some embodiments,maneuver event system 304 comprises a system for detecting maneuverevents (e.g., aggressive acceleration events, speeding events, hardcornering events, hard braking events, etc.). In various embodiments,maneuver event system 304 detects events using accelerometer data, videodata, speedometer data, steering data, or any other appropriate data. Insome embodiments, maneuver event system 304 is implemented using aprocessor. In some embodiments, proximity event system 306 comprises asystem for determining proximity events (e.g., events in which thevehicle is following too close). In various embodiments, proximity eventsystem 306 uses proximity data (e.g., from a proximity sensor), videodata, speedometer data, lane change data, or any other appropriate data.In some embodiments, proximity event system 304 is implemented using aprocessor. In some embodiments, lane change determiner 308 comprises alane change determiner for determining lane change data. In variousembodiments, lane change data comprises safe lane change data, laneleaving data, cut off data, moving over a lane marker data, or any otherappropriate lane change data. In some embodiments, lane changedeterminer 308 is implemented using a processor. In some embodiments,lane change data determined by lane change determiner 308 is used byproximity event system 306 for determining proximity events. In variousembodiments, event detector 300 additionally comprises a location eventsystem for determining location-based events, a driver behavior eventsystem for determining driver behavior events, a vehicle malfunctionevent system for determining vehicle malfunction events, or any otherappropriate event system.

FIG. 4 is a block diagram illustrating an embodiment of a sensorinterface. In some embodiments, sensor interface 400 comprises sensorinterface 204 of FIG. 2. In the example shown, sensor interface 400comprises vehicle system sensor interface 402 for communicating withvehicle system sensors. In some embodiments, vehicle system sensorinterface 402 comprises an on-board data (e.g., ODB) bus. In the exampleshown, sensor interface 400 additionally comprises accelerometerinterface 404 for communicating with one or more accelerometers, camerainterface 406 for communicating with one or more cameras, proximitysensor interface 408 for communicating with one or more proximitysensors, and GPS sensor interface 410 for communicating with one or moreGPS sensors. In some embodiments, sensor interface 400 additionallycomprises other interfaces for communicating with other sensors. In someembodiments, vehicle system sensor interface 402 receives reportsregarding a vehicle speed of the host vehicle of an event recorder and adistance to a forward vehicle. In some embodiments, proximity sensorinterface 408 receives reports regarding a distance to a forwardvehicle.

FIG. 5 is a block diagram illustrating an embodiment of a proximityevent system. In some embodiments, proximity event system 500 comprisesproximity event system 306 of FIG. 3. In some embodiments, received lanechange information is determined by lane change determiner 308 of FIG.3. In the example shown, proximity event system 500 comprises interface502 and processor 504. In various embodiments, interface 502 comprisesan input interface for receiving a lane change information, an inputinterface for receiving a host vehicle speed, an input interface forreceiving proximity data, an output interface for providing proximityevents, or any other appropriate interface. In the example shown,processor 504 comprises a processor for determining a proximity eventbased at least in part on lane change information (e.g., lane changeinformation received by interface 502). In some embodiments, interface502 is implemented using a processor. In some embodiments, interface 502is implemented using processor 504. In some embodiments, one or moreprocessors used to implement elements of proximity event system 500 areused to implement other systems (e.g., other event systems, sensorinterfaces, communications systems, etc.).

FIG. 6 is a diagram illustrating an embodiment of proximity data showinga proximity event. In some embodiments, the data shown in FIG. 6comprises proximity data (e.g., data received via proximity sensorinterface 408 of FIG. 4). In the example shown, a graph is depicted withthe y-axis of proximity to the vehicle as a function of time. The dataof the graph has a value of proximity near to a time close to the time=0that is at a typical proximity level (e.g., an appropriate followingdistance). At a first time (e.g., time t1), the measured proximitybegins to drop (e.g., indicating that the vehicle is approaching avehicle in front of it). The proximity (e.g., as measured using aproximity sensor) drops until it crosses a proximity time threshold attime t2 and hits a minimum at time t3. The proximity begins increasingat time t5 but not before a proximity event has been triggered at timet4—for example, the proximity event is triggered after the proximity isbelow the proximity time threshold for a duration of time past time t2of a sustained proximity time threshold (e.g., the proximity has beenbelow the proximity time threshold for a period of time equal to orlonger than the short proximity time threshold). A proximity event isprovided by a proximity event system (e.g., proximity event system 500of FIG. 5). In some embodiments, the proximity event is queued to beheld for a queue time before it is provided. In some embodiments, theproximity time threshold is the minimum time the driver needs to react,break and come to a full stop to avoid impact with a forward vehicle ifthat vehicle comes to a sudden stop. In some embodiments, a proximitytime threshold of 4 seconds is used when driving at freeway speed. Insome embodiments, the proximity time threshold is adjusted based atleast in part on the vehicle type as the stopping ability depends on thevehicle type's brakes and tires. In some embodiments, the proximity timethreshold is adjusted based at least in part on weather conditions—forexample, in rain or snow a higher proximity time threshold is used aswet surfaces reduce friction making it harder for the tires to grip andslow down. In some embodiments, the short proximity time threshold isthe time needed to estimate that the driver is not taking correctiveaction and keeps sustaining a risky distance to the forward vehicle. Insome embodiments, the short proximity time threshold is set to 2seconds. In various embodiments, the proximity time threshold and/or theshort proximity time threshold are configurable, are dynamicallyconfigurable (e.g., based on environmental conditions—for example,weather, lighting, traffic, etc.), or any other appropriate manner ofsetting the thresholds.

FIG. 7 is a diagram illustrating an embodiment of proximity data showinga cut off event. In some embodiments, the data shown in FIG. 7 comprisesproximity data (e.g., data received via proximity sensor interface 408of FIG. 4). In the example shown, a graph is depicted with the y-axis ofproximity to the vehicle as a function of time. The data of the graphhas a value of proximity near to a time close to the time=0 that is at atypical proximity level (e.g., an appropriate following distance). At afirst time (e.g., time t1), the measured proximity drops rapidly (e.g.,a distance of greater than a cut off distance threshold in a time lessthan a cut off time threshold, or faster than would be typical for anapproaching a car, e.g., in a discontinuous fashion). For example, in acase where the proximity distance is determined by radar, measured as around number of meters and reported every 0.1 seconds, a cut offthreshold of 1 meter and a cut off time threshold of 0.1 seconds can beapplied. In this case, in the event that a current proximity distance islower than the previous proximity distance by more than 1 meter, it isdetermined that the proximity distance has dropped rapidly. In someembodiments, the cut off threshold distance depends at least in part onthe resolution and accuracy of the sensor measuring the distance—forexample, a system using a machine vision sensor to detect forwardvehicles and their distances which has lower accuracy than a systemusing radar technology adopts a higher cut off threshold. In someembodiments, the rapid drop in proximity comprises a cut off event(e.g., the vehicle was cut off by another vehicle changing lanes closelyin front of it). In some embodiments, when a cut off event is detected,the sustained proximity time threshold for determining a proximity eventchanges from a short proximity time threshold to a long proximity timethreshold (e.g., the driver has additional time to return to anappropriate following distance after being cut off). At time t2, themeasured proximity increases past the proximity time threshold, wellbefore the long proximity time threshold (e.g., the extended sustainedproximity time threshold) occurs at time t3. No proximity event isprovided (e.g., to a server, to be stored on a server, etc.) even thoughthe measured proximity was below the proximity threshold for longer thanthe short proximity time threshold (e.g., the non-extended sustainedproximity time threshold. In various embodiments, the extended sustainedproximity time threshold is configurable, is dynamically configurable(e.g., based on environmental conditions—for example, weather, lighting,traffic, etc.), or any other appropriate manner of setting thethreshold.

FIG. 8 is a diagram illustrating an embodiment of proximity data showinga lane change event performed by the host vehicle. In some embodiments,the data shown in FIG. 8 comprises proximity data (e.g., data receivedvia proximity sensor interface 408 of FIG. 4). In the example shown, agraph is depicted with the y-axis of proximity to the vehicle as afunction of time. The data of the graph has a value of proximity near toa time close to the time=0 that is at a typical proximity level (e.g.,an appropriate following distance). At a first time (e.g., time t1) themeasured proximity begins to drop (e.g., the vehicle is approaching thevehicle in front of it). The proximity crosses the proximity timethreshold at time t2 (e.g., the driver is now following too close). Attime t3, the short proximity time threshold (e.g., the sustainedproximity time threshold) is crossed, and a proximity event is created.In some embodiments, the proximity event is queued for a queue time. Attime t4 (e.g., before the queue time), the measured proximity increasesrapidly (e.g., faster than would be typical for moving away from avehicle, e.g., in a discontinuous fashion). In some embodiments, therapid rise in proximity comprises a lane change event (e.g., the vehiclechanged lanes so that it is no longer behind the vehicle it waspreviously in close proximity to). In some embodiments, when a lanechange event is detected, any queued proximity events are removed (e.g.,the proximity event created at time t3 is removed from the queue)because the driver was in control of the situation and drove with aproximity distance under the proximity time threshold only to get closeto the forward vehicle before changing lanes to pass the forwardvehicle. No proximity event is provided even though the measuredproximity was below the proximity time threshold for longer than theshort proximity time threshold (e.g., the sustained proximity timethreshold).

FIG. 9 is a flow diagram illustrating an embodiment of a process fordetermining proximity events. In some embodiments, the process of FIG. 9is implemented by a proximity event system (e.g., proximity event system500 of FIG. 5). In the example shown, in 900, lane change information isreceived. In some embodiments, lane change information is received froma lane change determiner (e.g., lane change determiner 308 of FIG. 3).In 902, a proximity event is determined based at least in part on thelane change information.

FIG. 10 is a flow diagram illustrating an embodiment of a process fordetermining lane change information. In some embodiments, the process ofFIG. 10 is executed by a lane change determiner (e.g., lane changedeterminer 308 of FIG. 3). In some embodiments, lane change informationcomprises lane change information received by a process for determiningproximity events (e.g., received in 900 of FIG. 9). In the exampleshown, in 1000, sensor data is received. In various embodiments, sensordata comprises vehicle system sensor data, accelerometer data, cameradata, proximity sensor data, GPS data, or any other appropriate sensordata. In 1002, it is determined whether the sensor data comprises laneleaving information. In various embodiments, lane leaving informationcomprises an indication from a vision system of a vehicle leaving a lane(e.g., an indication determined based at least in part on a lanemarker), lane leaving information comprises a rapid increase inproximity (e.g., an increase rapid enough to indicate a lane shift toimmediately behind another vehicle), or lane leaving informationcomprises any other appropriate lane leaving information. In the eventit is determined that the sensor data does not comprise lane leavinginformation, control passes to 1006. In some embodiments, it isindicated that sensor data does not comprise lane leaving information inthe event that it is determined that the sensor data does not compriselane leaving information. In the event it is determined that the sensordata comprises lane leaving information, control passes to 1004. In1004, a lane leaving event is indicated, and the process ends. In 1006,it is determined whether the sensor data comprises cut off information.In various embodiments, cut off information comprises a rapid decreasein proximity (e.g., indicating being cut off by another vehicle),identification of a vehicle in a forward facing camera (e.g., thevehicle performing the cut off), or cut off information comprises anyother appropriate cut off information. In the event it is determinedthat the sensor data does not comprise cut off information, the processends. In some embodiments, it is indicated that the sensor data does notcomprise cut off information in the event it is determined that thesensor data not comprise cut off information. In the event it isdetermined that the sensor data comprises cut off information, controlpasses to 1008. In 1008, a cut off event is indicated.

FIG. 11 is a flow diagram illustrating an embodiment of a process fordetermining a proximity event based at least in part on lane changeinformation. In some embodiments, the process of FIG. 11 implements 902of FIG. 9. In the example shown, in 1100, proximity data is received. Insome embodiments, proximity data is received from a proximity sensor(e.g., via proximity sensor interface 408 of FIG. 4). In 1102, it isdetermined whether the vehicle speed is greater than a vehicle speedthreshold. In some embodiments, determining whether the vehicle speed isgreater than a vehicle speed threshold comprises determining a vehiclespeed. In some embodiments, a vehicle speed is received from a vehiclesystem sensor (e.g., via vehicle system sensor interface 402 of FIG. 4).In some embodiments, in the event a vehicle speed is below a vehiclespeed threshold (e.g., 20 miles per hour), proximity events are notdetected (e.g., the vehicle can navigate safely in close proximity toother vehicles at slow speeds). In the event it is determined that thevehicle speed is not greater than a vehicle speed threshold, the processends. In some embodiments, it is indicated that the vehicle speed is notgreater than a vehicle speed threshold in the event that it isdetermined that the vehicle speed is not greater than a vehicle speedthreshold. In the event it is determined that the vehicle speed isgreater than the vehicle speed threshold, control passes to 1104. Insome embodiments, it is indicated that the vehicle speed is greater thana vehicle speed threshold in the event that it is determined that thevehicle speed is greater than a vehicle speed threshold. In 1104, theprocess determines whether to provide a proximity event based at leastin part on lane change information. In various embodiments, it isindicated that a proximity event is provided, that a proximity event isnot provided, or any other appropriate indication.

FIG. 12 is a flow diagram illustrating an embodiment of a process fordetermining whether to provide a proximity event based at least in parton lane change information. In some embodiments, the process of FIG. 12implements 1104 of FIG. 11. In the example shown, in 1200, a proximitytime threshold and a sustained proximity time threshold are determined.In some embodiments, a sustained proximity time threshold is determinedbased at least in part on a cut off event. In some embodiments, aproximity time threshold is determined based at least in part on vehicledeceleration information. In 1202, it is determined whether there is avehicle detected within a proximity time threshold (e.g., whether aproximity sensor detects a vehicle within a proximity time threshold).In some embodiments, the proximity time threshold is based at least inpart on the vehicle speed (e.g., the proximity time threshold comprisesa longer time at higher speeds). In the event it is determined that novehicle is detected within a proximity time threshold, the process ends.In some embodiments, it is indicated that no vehicle is detected withina proximity time threshold in the event it is determined that no vehicleis detected within a proximity time threshold. In the event it isdetermined that a vehicle is detected within a proximity time threshold,control passes to 1204. In some embodiments, it is indicated that avehicle is detected within a proximity time threshold in the event it isdetermined that a vehicle is detected within a proximity time threshold.In 1204, it is determined whether a vehicle is within the proximity timethreshold for greater than the sustained proximity time threshold. Inthe event it is determined that a vehicle is not within the proximitytime threshold for greater than the sustained proximity time threshold,the process ends. In some embodiments, it is indicated that a vehicle isnot within the proximity time threshold for greater than the sustainedproximity time threshold, in the event that it is determined that avehicle is not within the proximity time threshold for greater than thesustained proximity time threshold. In the event it is determined that avehicle is within the proximity time threshold for greater than thesustained proximity time threshold, control passes to 1206. In 1206 aproximity event is queued. In some embodiments, a proximity event isqueued for a queue time before it is provided. In 1208, the processwaits for the queue time. In 1210, it is determined whether a laneleaving event was received while the proximity event was queued. In theevent it is determined that a lane leaving event was not received whilethe proximity event was queued, control passes to 1214. In the event itis determined that a lane leaving event was received while the proximityevent was queued, control passes to 1212. In 1212, the proximity eventis cancelled, and the process ends. In various embodiments, cancellingthe event comprises indicating to cancel the proximity event, indicatingthat the proximity event is cancelled, or any other appropriateindication. In 1214, the proximity event is released from the queue. Invarious embodiments, releasing the proximity event from the queuecomprises providing the proximity event, logging the proximity event,uploading the proximity event, or processing the proximity event in anyother appropriate way.

FIG. 13 is a flow diagram illustrating an embodiment of a process fordetermining a sustained proximity time threshold. In some embodiments,the process of FIG. 13 implements 1200 of FIG. 12. In the example shown,in 1300, proximity time threshold is set based on weather, vehicle type,road type, etc. For example, the proximity time threshold represents theminimum time a driver needs to react, brake and come to a full stop toavoid impact with a forward vehicle in the event that the forwardvehicle comes to a sudden stop. For example, a newer compact car withanti-lock braking system uses a proximity time threshold of 2.5 secondsand a sustained proximity time threshold of 2 seconds, while a heavytruck not equipped with anti-lock braking system uses a proximity timethreshold of 4 seconds and a sustained proximity time threshold of 3seconds; both proximity time thresholds are increased by 50% in the caseof raining or snowing conditions. In 1302, it is determined whether acut off event occurs close to proximity threshold crossing. In the eventthat a cut off event occurred close to proximity time thresholdcrossing, in 1304 a sustained proximity time threshold is set to a longproximity time threshold. For example, in the event that a compact carequipped with anti-lock braking system is following another vehicle witha proximity time of 5 seconds (i.e., a proximity time that is over theproximity time threshold) and a vehicle from an adjacent lane cuts inbetween producing suddenly a the proximity time of 1.5 seconds (i.e., aproximity time that is under the proximity time threshold), thesustained proximity time threshold is now increased from 2 to 3 secondsto allow the driver extra time to take corrective action and eliminatethe risk generated by the vehicle that cut in front of the vehicle. Inthe event that a cut off event did not occur close to proximity timethreshold crossing, in 1306 a sustained proximity time threshold is setto a short proximity time threshold. For example, a compact car equippedwith anti-lock braking system has a short proximity time threshold setto 2 seconds (e.g., its default sustained proximity time threshold).

Although the foregoing embodiments have been described in some detailfor purposes of clarity of understanding, the invention is not limitedto the details provided. There are many alternative ways of implementingthe invention. The disclosed embodiments are illustrative and notrestrictive.

What is claimed is:
 1. A system for determining proximity events,comprising: an input interface to receive a lane change information,wherein the lane change information includes sensor-collected data ofbehavior of a vehicle relative to at least one lane; and a processor to:determine a proximity event based at least in part on a distance betweenthe vehicle and a nearby vehicle being below a threshold distance for athreshold duration; determine whether to cancel the proximity eventbased at least in part on the lane change information; and if theproximity event is not cancelled, output the proximity event.
 2. Thesystem of claim 1, wherein the lane change information comprises a cutoff event.
 3. The system of claim 2, wherein the cut off informationcomprises a rapid decrease in proximity.
 4. The system of claim 2,wherein the cut off information comprises an identification of a vehiclein a forward facing camera.
 5. The system of claim 1, wherein the lanechange information comprises a lane leaving event.
 6. The system ofclaim 5, wherein the lane leaving information comprises an indicationfrom a vision system of a vehicle leaving a lane.
 7. The system of claim6, wherein an indication of leaving a lane by a vision system isdetermined based at least in part on a lane marker.
 8. The system ofclaim 5, wherein the lane leaving information comprises a rapid increasein proximity.
 9. The system of claim 1, wherein determining theproximity event comprises determining that a proximity sensor detects avehicle within a proximity time threshold.
 10. The system of claim 9,wherein the vehicle is within a proximity time threshold for greaterthan a sustained proximity time threshold.
 11. The system of claim 10,wherein the sustained proximity time threshold is increased in the eventthe lane change information comprises cut off information.
 12. Thesystem of claim 9, wherein the proximity event is canceled in the eventthe lane change information comprises lane leaving information.
 13. Thesystem of claim 9, wherein the proximity event is stored in a queue. 14.The system of claim 13, wherein the proximity event is released from thequeue in the event the lane change information does not comprise laneleaving information.
 15. The system of claim 13, wherein the proximityevent is released from the queue in the event it has been in the queuefor greater than a threshold time.
 16. The system of claim 1, whereindetermining the proximity event is based at least in part on a vehiclespeed.
 17. The system of claim 16, wherein a proximity time threshold isbased at least in part on the vehicle speed.
 18. The system of claim 16,wherein the proximity event is determined based at least in part onwhether the vehicle speed is greater than a vehicle speed threshold. 19.A method for determining proximity events for a vehicle, comprising:receiving a lane change information, wherein the lane change informationincludes sensor-collected data of behavior of a vehicle relative to atleast one lane; determining, using a processor, a proximity event basedat least in part on a distance between the vehicle and a nearby vehiclebeing below a threshold distance for a threshold duration; determining,using the processor, whether to cancel the proximity event based atleast in part on the lane change information; and if the proximity eventis not cancelled, outputting the proximity event.
 20. The system ofclaim 1, wherein determining the proximity event comprises determiningthat a proximity sensor detects a vehicle within a proximity timethreshold and the proximity time varies with road conditions.
 21. Acomputer program product for determining proximity events, the computerprogram product being embodied in a non-transitory computer readablestorage medium and comprising computer instructions for: receiving alane change information, wherein the lane change information includessensor-collected data of behavior of a vehicle relative to at least onelane; determining, using a processor, a proximity event based at leastin part on a distance between the vehicle and a nearby vehicle beingbelow a threshold distance for a threshold duration; determining, usingthe processor, whether to cancel the proximity event based at least inpart on the lane change information; and if the proximity event is notcancelled, outputting the proximity event.